Weather System and Message Overviews Document Version: 7.9 Date: July 27, 2020
Copyright © 2009-2023 Jeppesen. All rights reserved.
Your use of the AIM Bookshelf and all supporting documentation is subject to a separate license agreement between you and Jeppesen, a copy of which is included in the zip file or can be obtained from Jeppesen.
The AIM Bookshelf is delivered "AS IS" without warranty of any kind and is not guaranteed to be free from errors or defects. You rely on the AIM Bookshelf at your own risk. No support for the AIM Bookshelf is implied through its publication. The AIM Bookshelf is intended solely for use as a reference and examples of interfaces to Jeppesen systems. Jeppesen may revise, update or cease publication at any time, without notice. Building to the specifications set forth in the AIM Bookshelf does not mean that your intended integration needs will be met or that an interface will function as documented. We recommend contacting Jeppesen directly to discuss professional services options with respect to production application integration and validation efforts.
Document Revision History The following revision history table reflects all substantive changes to this document.
Table Of Contents
1 IntroductionThis document defines the interfaces which govern the interchange of data between a Weather system and other systems within an Airline Operation Center (AOC). Each AOC interface is represented by a message described in an associated XSD (XML Schema Definition). The XSD defines and enforces the required, optional, and conditional data that can be included in a message. Weather systems provide textual, graphical, and NOTAM information for the purposes of flight management. 1.1 AudienceThe intended audience for this document includes existing and potential Jeppesen customers, integration partners, and personnel with roles associated with application architecture, application development, system testing, implementation, and application support within Weather. 1.2 ScopeThis document discusses the Weather messages currently supported by the Jeppesen Solution Integrator. Each message description includes the following:
Other data interfaces or formats not included in this document will be considered custom and not supported. 1.3 XML Schema/XSDThe XML schema for this ICD is published in the following file: Weather.XSD 1.4 Key Concepts1.4.1 Weather DataWeather data is received from external sources into an AOC’s Weather system. Once there, the data is processed and correlated where it can be retrieved and provided to other AOC systems. Weather sources are varied and include such entities as the National Weather Service, FAA, and Jeppesen NOTAM Service. Weather Data includes reports such as METARS, TAFS, SIGMETS, and NOTAMS. 2 Message SummaryTable 2-1 lists the messages that can be sent or handled by the application. The messages originated by this application (messages that begin with “WX”) are further discussed in Section 3 AOC Interface Messages.
3 AOC Interface MessagesThe following messages are processed by the Weather system. 3.1 WX001 – Point Query3.1.1 Message OverviewSystems within the AOC can request weather data from the Weather system. The Point Query message allows these systems to request weather for a specific point (location and time) in an appropriate format (product). This message is often used to create a weather briefing, which consists of weather data for multiple locations.
The Weather system receives a request for this data, processes the request and then returns the requested report (product) to the other AOC system. For example, the Dispatch system requests weather information related to Flight 1234 from LAX to SFO. In a single Point Query message, Dispatch requests weather for the following points and times: LOCATION TIME PRODUCT
LAX AUGUST 10, 2007 0900 TAF, PIREP SFO AUGUST 10, 2007 1010 TAF, PIREP The Weather system processes the request and then sends a single Point Query response message to the Dispatch system containing four groups of data:
3.1.2 Message System FlowThis message interacts with the systems as shown in Figure 1. 3.1.3 Message DetailsThe following table provides details on the message version and includes links to the message’s technical specification.
3.2 WX002 – WMO Query3.2.1 Message OverviewThe WMO query request accepts the WMO header and the version of the weather products. Multiple versions of the header may be retrieved in a single request. Following is the data definition explaining attributes and elements in the request and response. 3.2.2 Message System FlowThis message interacts with the systems as shown in Figure 2. The following table provides details 3.2.3 Message Detailson the message and includes links to the message’s technical specification.
3.3 WX003 – Weather Notification3.3.1 Message OverviewThis message is published to other systems within an AOC when certain ceiling or visibility thresholds are met. These alert thresholds are configured within the Weather system. For example, JEPP Airlines has configured their weather system to alert the dispatcher when the ceiling at Denver International (DEN) drops below 2000 feet. On August 17 at 0900, the ceiling crosses this threshold. The Weather system automatically sends the Dispatch system a notification, which includes:
3.3.2 Message System FlowThis message interacts with the systems as shown in Figure 3. 3.3.3 Message DetailsThe following table provides details on the message and includes links to the message’s technical specification.
|
This message allows customers to pass weather information from a WSI weather feed source through AOCi to consuming weather products and services.
This message interacts with the systems as shown in Figure 4.
The following table provides details on the message and includes links to the message’s technical specification.
Message Version |
WX004 v1 |
Message Header Details |
msgName: WX004 |
Message Specification |
|
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | No changes. *** 10-2-19 edit: No Version Change: Removed WX004v1WSIWeatherFeed.xml, and WX004BWSIWeatherFeed.xml sample |
Systems within the AOC can request weather data from the Weather system. The Point Query message allows these systems to request weather for a specific point (location and time) in an appropriate format (product). This message is often used to create a weather briefing, which consists of weather data for multiple locations.
The Point Query request includes the following primary fields:
The Weather system receives a request for this data, processes the request and then returns the requested report (product) to the other AOC system.
For example, the Dispatch system requests weather information related to Flight 1234 from LAX to SFO. In a single Point Query message, Dispatch requests weather for the following points and times:
The Weather system processes the request and then sends a single Point Query response message to the Dispatch system containing four groups of data:
This message interacts with the systems as shown in Figure 5.
The following table provides details on the message version and includes links to the message’s technical specification.
Message Version |
WX005 v14 |
Message Header Details |
msgName: WX005 PointQueryRequest / Response |
Message Header Details |
msgName: WX005 SignificantRequest / Response |
Message Specification |
WX005 WeatherServiceRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Version 3:
* Added GAMET enumeration to SignificantWxProductNameType causes updates. Added 3 enumerations to WX011 productTitle defined as GraphicWxImages type: Accumulated Precipitation Mosaic, Global Visible Satellite Imagery, Forecast Radar Mosaic. Additions of enumerations to WxImages type also changes WX003, WX012, WX014. |
This message allows customers to pass weather information from a weather feed source through AOCi to weather and dispatch products and services.
This message interacts with the systems as shown in Figure 6.
The following table provides details on the message version and includes links to the message’s technical specification.
Message Version |
WX006 v1 |
Message Header Details |
msgName: WX006 |
Message Specification |
|
Defined in XSD |
|
Sample Messages |
|
Message Version History | Updated message. |
This message is used by aircraft to request weather information. The typical information flow is as follows:
This message interacts with the systems as shown in Figure 7.
The following table provides details on the message version and includes links to the message’s technical specification.
Message Version |
WX007 v8 |
Message Header Details (REQUEST/RESPONSE) |
msgName: WX007 |
Message Specification |
WX007 EnrouteWeatherRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Updated sample message
Version 2: * Updated route string Version 3: * Updated Request message: optl element for minimumRunwayLength, UOM is 100's feet; optl element for maximumAirportElevation, UOM is feet. Optl element for crashFireIndex, string; optl element for swathWidth, UOM is NM; Added responseFormat (raw, decoded, both); make routeString required; Updated Response message: optl element for minimumRunwayLength, UOM is 100's feet; optl element for maximumAirportElevation, UOM is feet. Optl element for crashFireIndex, string; optl element for swathWidth, UOM is NM; make routeString required. Version 4: * Added coordinates/latitude, longitude (GeographicPointType) to PqPwResponseBodyDataGroupType for support of raw winds aloft data. Data group exists in: WX007 v4 REQUEST/RESPONSE enrouteWxResponse / pointQueryRawDecodedResponse /pointQueryRawDecodedResponse / pqResponseBodyDataType /pqPwResponseBodyDataGroup. * WX007 v4 Added EnrouteWeatherResponse / pointQueryRawDecodedResponseGroupType - adds geographicPointType / latitude, longitude because of the shared pointQueryRawDecodedGroupType from WX005. NOTE: geographicPointType / latitude, longitude is not contained in the WX007 request. Version 5: * Add AIRMET and SIGMET to the WX007 Response (changes WX003, WX005, WX007, WX014 responses). Changed enrouteWeatherGroup/responseFormat to required. Version 6: * Added VAAC to productName, and decoded volcanicAshAdvisory structure to response. Version 7: * Added required element to WX007 request that is repeatable where a value of one or many may be selected: TAF, METAR, WAFD, PIREP, SIGMET, AIRMET, VAAC, WSI FPG, WSI SIGMET. Version 8: * Added GAMET enumeration to SignificantWxProductNameType causes updates. |
This message allows customers to pass turbulence-related weather information from a WSI weather feed source through AOCi to consuming weather products and services.
This message interacts with the systems as shown in Figure 8.
The following table provides details on the message version and includes links to the message’s technical specification.
Message Version |
WX008 v1 |
Message Header Details (RESPONSE) |
msgName: WX008 |
Message Specification |
|
Defined in XSD |
|
Sample Messages |
|
Message Version History | No changes. |
The TAF Consolidator service is intended to construct and present to the requesting Client applications a Decoded Consolidated TAF structure and related TAFs used to construct the Consolidated TAF. The intent is to use the TAF Consolidator service to support Client applications (e.g. Jeppesen Dispatch Control and JetPlan Engine), but may extend to customers with 2 TAF forecast source providers.
With two source providers of TAF forecasts, the Client applications have the challenge of selecting the right forecast for a specific time or time range and Station/Airport according to specific selection rules. The intent of the TAF Consolidator service is to alleviate the clients of the need to select from the sources and to provide a single time block segregated TAF structure that has provided the TAF source selection according to defined selection rules for each specific time block for the requested time period. That way, each client application can use the Decoded Consolidated TAF by time blocks and use that information in its internal logic or functionality. Since the selection logic is provided by the TAF Consolidator service, there is no need for each client to implement separate selection logic.
The TAF Consolidator Service will support a Response for the requesting Client. The response will include a Decoded Consolidated TAF structure related to the Stations (airports) provided in the request and related to the current time (request time) or a given time of interest provided in the request. For each Station and requested time block in the Request, the response will also include a full copy of the TAFs from each source that are a component of the decoded consolidated TAF. For the requested time period for each Station, this could involve several individual TAFs from each source.
This message interacts with the systems as shown in Figure 9.
The following table provides details on the message version and includes links to the message's technical specification.
Message Version |
WX009 v3 |
Message Header Details (REQUEST/RESPONSE) |
msgName: WX009 |
Message Specification |
WX009 ConsolidatedWeatherSourcesQueryType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Version 1: |
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message version and includes links to the message's technical specification.
Message Version |
WX010 vA |
Message Header Details (REQUEST/RESPONSE) |
msgName: WX010 |
Message Specification |
WX010 HazardousWxRiskAlertsRequestType |
Defined in XSD |
|
Sample Messages |
Samples not yet available for this message version. |
Message Version History | Version A: |
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message version and includes links to the message's technical specification.
Message Version |
WX011 v9 |
Message Header Details (REQUEST/RESPONSE) |
msgName: WX011 |
Message Specification |
WX011 AvailableGraphicWxImagesRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Version A: |
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message version and includes links to the message's technical specification.
Message Version |
WX012 v8 |
Message Header Details (REQUEST/RESPONSE) |
msgName: WX012 |
Message Specification |
WX012 GraphicWxImagesRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Version A: |
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message and includes links to the message’s technical specification.
Message Version |
WX013 v1 |
Message Header Details |
msgName: WX013 |
Message Specification |
|
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Initial message.
Version 1: * Updated WX012 messageCatalogTemplate to WX013 to v1, and MessageChangeList. |
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message and includes links to the message's technical specification.
Message Version |
WX014 v9 |
Message Header Details |
msgName: WX014 |
Message Specification |
WX014 WeatherNotificationRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Initial message.
|
The Message Overview for this version is not yet available for this DRAFT version.
A Message Systems Flow diagram is not yet available for this DRAFT version.
The following table provides details on the message and includes links to the message's technical specification.
Message Version |
WX015 v6 |
Message Header Details |
msgName: WX015 |
Message Specification |
WX015 GlobalWxInEffectRequestType |
Defined in XSD |
|
Sample Messages |
Samples not available for this message version. |
Message Version History | Version 1: |